-
-
Notifications
You must be signed in to change notification settings - Fork 830
Conversation
d3bd43d
to
5a1e5d0
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What do we get from using AccessibilityButton without its accessible keyboard handling? Why not just switch to Compound button for usecases which need disableKeyboardOverrides
Because, it means add all the glue to between the EW tooltip and the compound button. |
We have a 50/50-ish mix of Compound/local tooltips already, so please do not consider that a blocker, preferring Compound tooltips going forward |
Okay, I'll discard the use of the |
Compund ftw |
This reverts commit 5a1e5d0
2f2295f
to
0387697
Compare
59cee43
to
fbee2ad
Compare
c6e0662
to
1b840d7
Compare
Checklist
Closes element-hq/element-web#27016
The compound Menu component is putting the keyboard listeners on the trigger through the props but the
AccessibilityButton
is already handling some keyboard events.Enregistrement.de.l.ecran.2024-02-28.a.16.54.25.mov